EX 2013 Database Copy "Passive Failed" but "Content Index State Healthy" suspend/remove?

Hello,
I had a failure during the replication of my db copies on my DAG the other night, and I am unsure what my next steps should be to get a healthy copy for the failed server.  I was expecting to see a Suspend | Update | Remove option, but all I get is suspend & remove.  See details below...

What should my next steps be to get a good copy of the db on my MBX01 server?  Will it just fix itself at the next attempt to replicate, or do I need to manually do something to make a fresh copy?

Thanks in advance for any help!

-------------------------------------------------------------------

DB01 Database availability group: EX-DAG01 Servers VM-MBX-01 VM-MBX-02 Database copies CVAE-DB01\VM-MBX-01
Passive Failed
Copy queue length: 74246
Content index state: Healthy
Suspend | R
emove
View Details CVAE-DB01\VM-MBX-02
Active Mounted
Copy queue length: 0
Content index state: Healthy
View Details


  • Edited by Mousikos2 16 hours 13 minutes ago
April 21st, 2015 11:15am

Use powershell:

Resume-MailboxDatabaseCopy

if that fails:

Update-MailboxDatabaseCopy -Identity DB1\MBX1 -DeleteExistingFiles

Free Windows Admin Tool Kit Click here and download it now
April 21st, 2015 5:52pm

Hi Mousikos2,

Thank you for your question.

In addition, if Andys solution didnt work, we could run the following command to check if the issue persist:

Suspeend-MailboxDatabaseCopy Identity Databasename\Mailbox Server Name

Then run:

Update-MailboxDatabaseCopy Identity Databasename\Mailbox Server Name DeleteExistingFiles

The duration of the seeding process will depend on the size of the database and the speed of the network. When the update has completed it will automatically resume replication for the database copy.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

April 22nd, 2015 1:49am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics